Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content Skip to complementary content

Preparing Microsoft Azure SQL Managed Instance backup and recovery

Qlik Replicate consumes changes captured from the database transaction log (TLOG). The TLOG is maintained by Microsoft Azure SQL Managed Instance for recovery purposes. All changes made to a database are written to the TLOG. The following happens when recovery is required:

  • A backup copy of the database is made.
  • Logged events are taken and used in a rolling-forward process where the recorded changes are replayed against that copy.

To prepare for backup and recovery you must make sure that the Microsoft Azure SQL Managed Instance Recovery Model is set up. You select the Recovery Model in the Microsoft Azure SQL Managed Instance Management Studio. This should be carried out by a Microsoft Azure SQL Managed Instance system administrator.

The TLOG data is truncated as soon as it is no longer needed therefore the TLOG is not persistent. However, Qlik Replicate guaranteed delivery requires persistency in the changed data. To ensure persistency:

  • A full database backup must be carried out before beginning to replicate data.
  • The Recovery Model must be set to Bulk logged or Full.

To set the recovery model

In the database properties Options tab, set the Recovery Model to Bulk logged or Full. In these modes, the transaction Log is more durable.

Information note

After setting the Recovery Model, it is strongly recommended not to change it; doing so may result in loss of data.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!